About: Generalized date-time description

This page provides a structured representation (serialized as HTML+RDFa) of the description of the entity denoted ("referred to") by the hyperlink that anchors the About: <Entity Label> text at the top.

The data is presented here in the form of a collection of Entity->Attribute->Value (EAV) or Subject->Predicate->Object (SPO) relations.

In conformance with core Web Architecture, the same description data may also be retrieved in a variety of other negotiable serialization formats, which currently include CSV, HTML+Microdata, (X)HTML+RDFa, N-Triples, Turtle, N3, RDF/JSON, JSON-LD, RDF/XML, Atom, and CXML.

Why is this page important?

This page and its neighbors provide 5-Star Linked Data URIs (Web Super Keys) for HTTP-accessible data. These URIs are powerful starting points for serendipitous data discovery using the Web's "follow your nose" pattern, as well as a key ingredient for SPARQL queries over HTTP, ODBC, JDBC, ADO.NET, OLE-DB, or XMLA connections.

A single link from this page can be the seed of a powerful Web traversal, en route to discovery and exploitation of unimagined insights, using existing tools such as browsers, spreadsheets, business intelligence and analytics packages, basic report writers, presentation generators, project management packages, and many others.

How can I discover more structured data like this?

A variety of discovery pointers are available to users and user agents (software programs) that include:

<link /> relations embedded within the <head /> section of each description page
"Link:" response headers included as part of HTTP response metadata.

Can I expose my own Web resources this way?

Yes! Simply include entries, based on the example below, in the <head/> section of your (X)HTML page, whether static or dynamically generated --

<link rel="related"
    title="My Data in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/<scheme-part-of-url>/<host-part-of-url>/<path-part-of-url>"
    />

The scheme part is the first bit of a URI, up to but not including the first colon (":"). The host part includes the port, if any, and is found between the double solidus ("//") following the first colon, and the first solidus ("/") thereafter. The path part is everything thereafter (possibly including a query part or fragment identifier part).

For example, if your original page were at --

http://en.wikipedia.org/wiki/Linked_Data

-- the scheme part is "http", the host part is "en.wikipedia.org", and the path part is "wiki/Linked_Data". You could therefore provide access to a Linked Data graph rendition by including a <head/> entry like this --

<link
    rel="related"
    title="Linked data - Wikipedia, the free encyclopedia - in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/http/en.wikipedia.org/wiki/Linked_Data"
    />

Additional Information

URIBurner.com -- a live service that produces pages like this
OpenLink Data Explorer (ODE) -- a browser plug-in that enables you to browse and bookmark Linked Data pages via additions to the browser menus, both main and contextual
- ODE usage examples

Sponging disallowed (Read-only view)

Description of date and time structured with separate values for the various elements of a calendar-clock system

Subject of Relation
Object of Relation

Property	Value
type	Classhttp://www.w3.org/2002/07/owl#Class
subClassOf	Temporal positionhttp://www.w3.org/2006/time#TemporalPosition nodeID://b50857694nodeID://b50857694 nodeID://b50857695nodeID://b50857695 nodeID://b50857696nodeID://b50857696 nodeID://b50857697nodeID://b50857697 »more»
label	Generalized date-time description (en) descripción de fecha-hora generalizada (es)
comment	Descripción de fecha y hora estructurada con valores separados para los distintos elementos de un sistema calendario-reloj. (es) Description of date and time structured with separate values for the various elements of a calendar-clock system (en)
note	Algunas combinaciones de propiedades son redundantes - por ejemplo, dentro de un 'año' especificado si se proporciona 'día del año' entonces 'día' y 'mes' se pueden computar, y viceversa. Los valores individuales deberían ser consistentes entre ellos y con el calendario, indicado a través del valor de la propiedad 'tiene TRS'. (es) Some combinations of properties are redundant - for example, within a specified :year if :dayOfYear is provided then :day and :month can be computed, and vice versa. Individual values should be consistent with each other and the calendar, indicated through the value of the :hasTRS property.
definition	Descripción de fecha y hora estructurada con valores separados para los distintos elementos de un sistema calendario-reloj. Description of date and time structured with separate values for the various elements of a calendar-clock system (en)

Property	Value
subClassOf	Date-Time descriptionhttp://www.w3.org/2006/time#DateTimeDescription
first	nodeID://b50857748nodeID://b50857748
domain	dayhttp://www.w3.org/2006/time#day day of weekhttp://www.w3.org/2006/time#dayOfWeek day of yearhttp://www.w3.org/2006/time#dayOfYear hourhttp://www.w3.org/2006/time#hour minutehttp://www.w3.org/2006/time#minute »more»
range	has Date-Time descriptionhttp://www.w3.org/2006/time#hasDateTimeDescription in date-time descriptionhttp://www.w3.org/2006/time#inDateTime